[release/7.0] load quic early to prevent interaction with tests #75603
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport of #75488 to release/7.0
Fixes #75484
/cc @wfurt @karelz @CarnaViire
Customer Impact
Test only change to stabilize networking tests - avoid crashes on
arm64-Mono
due to a bug inlttng
(dependency ofMsQuic
).Essentially the same as #75424 but for
System.Net.Security
andSystem.Net.Mail
-- details:When msquic is loaded it will also initialize
lttng
. That callswait
and it can reap processes fromRemoteExecutor
and that will cause Assert inProcess
code. (long story and evidence is in #74795)While the problem really lives in
lttng
there is no quick fix for that. To void the problem this change tries to loadMsQuic
early via static variable and that will initializelttng
before any tests actually start.Testing
CI
Risk
Low. Test-only change